Priority based application event control (PAEC) to reduce power consumption

ABSTRACT

Methods and apparatus relating to Priority Based Application Event Control (PAEC) to reduce application events are described. In one embodiment, PAEC may determine which applications (and their corresponding sub-system(s)) may cause a processor or platform to exit a low power consumption state. In an embodiment, PAEC may determine which applications (and their corresponding sub-system(s)) may resume operations after a processor or platform exit a low power consumption state. Other embodiments are also claimed and disclosed.

FIELD

The present disclosure generally relates to the field of electronics.More particularly, an embodiment of the invention relates to PriorityBased Application Event Control (PAEC) to reduce power consumption incomputing devices.

BACKGROUND

Generally, one of the highest power consuming components in computingsystem is a processor. To reduce power consumption, some implementationsmay attempt to have the processor enter a sleep or standby mode as oftenand as long as possible. However, these attempts may be defeated due tooccurrence of various events, e.g., triggered by other components in thesystem, which may force a processor to exit a lower power consumptionstate.

In turn, the higher power consumption may also increase heat generation.Excessive heat may damage components of a computer system. Further, thehigher power utilization may increase battery consumption, e.g., inmobile computing devices, which in turn reduces the amount of time amobile device may be operated prior to recharging. The additional powerconsumption may additionally require usage of larger batteries that mayweigh more. Heavier batteries reduce the portability or usability of amobile computing device.

Accordingly, overall system power consumption and utility may bedirectly related to how long a processor is maintained in a lower powerconsumption state.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is provided with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIGS. 1, 3 and 5-6 illustrate block diagrams of embodiments of computingsystems, which may be utilized to implement various embodimentsdiscussed herein.

FIG. 2 illustrates a block diagram of portions of a processor core andother components of a computing system, according to an embodiment.

FIG. 4 illustrates a flow diagram in accordance with some embodiments.

DETAILED DESCRIPTION

in the following description, numerous specific details are set forth inorder to provide a thorough understanding of various embodiments.However, various embodiments of the invention may be practiced withoutthe specific details. In other instances, well-known methods,procedures, components, and circuits have not been described in detailso as not to obscure the particular embodiments of the invention.Further, various aspects of embodiments of the invention may beperformed using various means, such as integrated semiconductor circuits(“hardware”), computer-readable instructions organized into one or moreprograms (“software”), or some combination of hardware and software. Forthe purposes of this disclosure reference to “logic” shall mean eitherhardware, software, firmware, or some combination thereof. Also, the useof “instruction” and “micro-operation” (uop) is interchangeable asdiscussed herein.

Some of the embodiments discussed herein may utilize Priority BasedApplication Event Control (PAEC) to reduce the number of applicationevents that may cause a processor to exit a low power consumption state.In one embodiment, PAEC may be utilized in mobile devices or any othertype of computing device. In an embodiment, PAEC techniques may leveragehardware (e.g., SoC (System on Chip) or On-Die System Fabric (OSF)) toassign priorities to applications (“apps”) and associate theseapplication priorities or applications with platform sub-system states(modes), e.g., to control platform events generated by bothplatform-power-aware and/or platform-power-unaware applications based onpriority and/or policy configuration, e.g., without compromising QOS(Quality Of Service) or user experience. In one embodiment, PAECprovides fine grain power management by associating applications withthe platform sub-system(s), e.g., to provide a mechanism to specifyand/or prioritize which apps may wake the system or processor, whichapps must/may run after system-wakeup or processor-wakeup, etc., andwithout impacting the QOS requirements and/or user experience.

In some embodiments, resumption of one or more applications (after aplatform/system and/or a processor have entered a low power consumptionstate) may be restricted by the PAEC based on some policy (also referredto herein interchangeably as configuration) information or settings.This information may be adaptive and change during runtime in someembodiments. Furthermore, this policy information may includeinformation regarding whether, in which order, when, and/or which of theone or more applications and/or their associated sub-system(s) are to bewoken once the platform/system and/or the processor exits from the lowerpower consumption state. In an embodiment, the policy information mayalso indicate and/or prioritize which application and/or sub-system maywake the system.

The techniques discussed herein may be used in any type of a computingsystem, such as the systems discussed with reference to FIGS. 1-2 and5-6. More particularly, FIG. 1 illustrates a block diagram of acomputing system 100, according to an embodiment of the invention. Thesystem 100 may include one or more processors 102-1 through 102-N(generally referred to herein as “processors 102” or “processor 102”).The processors 102 may communicate via an interconnection network or bus104. Each processor may include various components some of which areonly discussed with reference to processor 102-1 for clarity.Accordingly, each of the remaining processors 102-2 through 102-N mayinclude the same or similar components discussed with reference to theprocessor 102-1.

In an embodiment, the processor 102-1 may include one or more processorcores 106-1 through 106-M (referred to herein as “cores 106” or moregenerally as “core 106”), a shared cache 108, a router 110, and/or alogic 120. The processor cores 106 may be implemented on a singleintegrated circuit (IC) chip. Moreover, the chip may include one or moreshared and/or private caches (such as cache 108), buses orinterconnections (such as a bus or interconnection network 112), memorycontrollers (such as those discussed with reference to FIGS. 5-6), orother components.

In one embodiment, the router 110 may be used to communicate betweenvarious components of the processor 102-1 and/or system 100. Moreover,the processor 102-1 may include more than one router 110. Furthermore,the multitude of routers 110 may be in communication to enable datarouting between various components inside or outside of the processor102-1.

The shared cache 108 may store data (e.g., including instructions) thatare utilized by one or more components of the processor 102-1, such asthe cores 106. For example, the shared cache 108 may locally cache datastored in a memory 114 for faster access by components of the processor102. In an embodiment, the cache 108 may include a mid-level cache (suchas a level 2 (L2), a level 3 (L3), a level 4 (L4), or other levels ofcache), a last level cache (LLC), and/or combinations thereof. Moreover,various components of the processor 102-1 may communicate with theshared cache 108 directly, through a bus (e.g., the bus 112), and/or amemory controller or hub. As shown in FIG. 1, in some embodiments, oneor more of the cores 106 may include a level 1 (L1) cache 116-1(generally referred to herein as “L1 cache 116”).

In one embodiment, the PAEC logic 120 may reduce the number ofapplication events that may cause a processor/platform to exit a lowpower consumption state and/or restrict resumption of operations byapplications (and powering on of their corresponding sub-systems) aftera processor/platform exits a low power consumption state. Logic 120 mayassign priority to applications (“apps”) that may be stored in memory114 and may further associate the apps with platform sub-system states(modes), e.g., to control platform events generated by bothplatform-power-aware and/or platform-power-unaware applications based onapplication priority and/or policy configuration, e.g., withoutcompromising QOS (Quality Of Service) or user experience. In someembodiments, operations performed by logic 120 may be controlled orconfigured via OS and/or software application(s) (e.g., that may bestored in the memory 114), e.g., per user or Original EquipmentManufactures (OEMs) (based on information from a User Interface (e.g.,UI 314 of FIG. 3) in some embodiments). Additionally, informationrelating to the application priority and/or application policyconfiguration may be stored in any of the memories discussed herein,including for example, memory 114 and/or caches 108/116, etc.

FIG. 2 illustrates a block diagram of portions of a processor core 106and other components of a computing system, according to an embodimentof the invention. In one embodiment, the arrows shown in FIG. 2illustrate the flow direction of instructions through the core 106. Oneor more processor cores (such as the processor core 106) may beimplemented on a single integrated circuit chip (or die) such asdiscussed with reference to FIG. 1. Moreover, the chip may include oneor more shared and/or private caches (e.g., cache 108 of FIG. 1),interconnections (e.g., interconnections 104 and/or 112 of FIG. 1),control units, memory controllers, or other components.

As illustrated in FIG. 2, the processor core 106 may include a fetchunit 202 to fetch instructions (including instructions with conditionalbranches) for execution by the core 106. The instructions may be fetchedfrom any storage devices such as the memory 114 and/or the memorydevices discussed with reference to FIGS. 5-6. The core 106 may alsoinclude a decode unit 204 to decode the fetched instruction. Forinstance, the decode unit 204 may decode the fetched instruction into aplurality of uops (micro-operations). Additionally, the core 106 mayinclude a schedule unit 206. The schedule unit 206 may perform variousoperations associated with storing decoded instructions (e.g., receivedfrom the decode unit 204) until the instructions are ready for dispatch,e.g., until all source values of a decoded instruction become available.In one embodiment, the schedule unit 206 may schedule and/or issue (ordispatch) decoded instructions to an execution unit 208 for execution.The execution unit 208 may execute the dispatched instructions afterthey are decoded (e.g., by the decode unit 204) and dispatched (e.g., bythe schedule unit 206). In an embodiment, the execution unit 208 mayinclude more than one execution unit. The execution unit 208 may alsoperform various arithmetic operations such as addition, subtraction,multiplication, and/or division, and may include one or more anarithmetic logic units (ALUs). In an embodiment, a co-processor (notshown) may perform various arithmetic operations in conjunction with theexecution unit 208.

Further, the execution unit 208 may execute instructions out-of-order.Hence, the processor core 106 may be an out-of-order processor core inone embodiment. The core 106 may also include a retirement unit 210. Theretirement unit 210 may retire executed instructions after they arecommitted. In an embodiment, retirement of the executed instructions mayresult in processor state being committed from the execution of theinstructions, physical registers used by the instructions beingde-allocated, etc.

The core 106 may also include a bus unit 214 to enable communicationbetween components of the processor core 106 and other components (suchas the components discussed with reference to FIG. 1) via one or morebuses (e.g., buses 104 and/or 112). The core 106 may also include one ormore registers 216 to store data accessed by various components of thecore 106 (such as values related to assigned app priorities and/orsub-system states (modes) association.

Furthermore, even though FIG. 1 illustrates the PAEC logic 120 to becoupled to the core 106 via interconnect 112, in various embodiments thePAEC logic 120 may be located elsewhere such as inside the core 106,coupled to the core via bus 104, etc.

Moreover, the current generation of smart phones and netbooks platformsmay support granular power management via OSPM (Operating System PowerManagement), PMU (Power Management Unit), and SCU (System ControllerUnit). The SCU along with the Operating System may provide the Always OnAlways Connected (AOAC) capability to the platform. Based on the OSpower manager's guidance, the SCU may determine the correct power levelfor different sub-systems (including CPU (Central Processing Unit) orprocessor) in the platform. External events like timer interrupt,interrupt from Communication (Comms) module, etc., may be forwarded bythe SCU to CPU thereby waking up the CPU. Apart from subsysteminterrupts, CPU also may be woken up by applications (apps) due totimers or events to provide AOAC functionality. These wake(s) reduce theresidency time of the CPU in the sleep or deep sleep state, resulting inadditional power consumption. Also, platform power-unaware apps may beactive resulting in waking of the CPU and other sub-systems, even thoughthe power manager entity has put the platform into standby/sleep mode.In addition, applications may set timers and wake up the CPUperiodically even though there is no change to a resource underconsideration.

Furthermore, some current platforms may support coalescing of externalevents, and wait/deliver the events (wakes) based on some wakeconfiguration. Current implementations generally have no way to assignpriority to the applications in the platform and associate theseapplication priorities with different operating modes of the platform(such as browsing, video playback, etc.), and as a result, apps may befrozen/thawed—put into sleep/deep sleep/standby state or forced to be insuspended state or allowed to be run. In addition, there is generally noexisting mechanism to specify and prioritize which apps may wake thesystem from Suspended state and also, which apps must/may run onceplatform wakes up, etc. For example, in some current systems, SCUcontrols only the sub-system states and not the apps associated withthem. Also, current methodologies generally fail to consider the QOS oruser experience impact on application/sub-system that are forced intosleep/standby state.

FIG. 3 illustrates a block diagram of a system 300 in which PAECtechniques may be implemented, according to some embodiments. To providethe compute and storing capability, system 300 may include a host CPU(or GFX (Graphics) 302 (such as the processors discussed with referenceto FIGS. 1-2 and 5-6), memory 304 (such as the memories discussed withreference to FIGS. 1-2 and 5-6), and drives (e.g., as part of subsystems 1 through X). Generally, the sub-systems shown (e.g., 1, 2,through X) may include any component in a computing system such as thecomponents discussed with reference to FIGS. 1-2 and 4-6, that arecapable of being power gated and/or capable of waking a computingsystem/platform and/or processor.

Furthermore, system 300 may include a display controller 308 to providedisplay capabilities, a hardware Security Engine 310 to provide anynecessary cryptographic operations and/or a tamper proof executionenvironment, a PAEC component 312 implemented as an OS component to runinside the OS 313 (wherein PAEC 312 may be tightly integrated with thescheduler of the OS 313 and an OS power manager in one embodiment andhave the ability to halt/freeze/thaw a currently-running process/programand resume later in some embodiments), a PAEC UI (User Interface) 314(which may be an application component in accordance with oneembodiment) to provide the ability for an administrator or user tospecify priority and/or associate them with the modes of the sub-systemsin the platform, a Secure Storage 316 to provide a tamper proof securestorage that stores the PAEC policy configured by user/administratorinformation, and a SCU (System Controller Unit) and/or PMU (PowerManagement Unit) 318 to provide fine-grained platform power managementsupport.

FIG. 4 illustrates a flow diagram of a method for implementing PAEC,according to some embodiments. In an embodiment, FIG. 4 illustrates theoperation of the PAEC logic 120, PAEC component 312, and/or PAEC UI 314in accordance with some embodiments. Furthermore, the operationsdiscussed with reference to FIG. 4 may be performed by one or morecomponents of FIGS. 1-3 and 5-6.

Referring to FIGS. 1-4, once PAEC functionality is enabled at 402 and/orPAEC UI is invoked at 403 (e.g., by a user/OEM/OS/etc. and per somestored value such as a bit), the PAEC UI 314 may provide the user withthe current policy settings stored in the security storage 316 at 404.PAEC UI 314 may provide the user with option(s) to change the policyand/or priority settings at 406. At 408, PAEC UI 314 may allow a user oradministrator to assign priority to the applications and associate themwith sub-system operating mode(s) (e.g., Browsing, Video playback,etc.), e.g., to update the policy settings.

In an embodiment, priority may be assigned by an OEM, OS, or appsprovider at 408. Furthermore, priority may be determined and assignedbased on QOS API (Application Program Interface) requirements placed bythe app during application registration, in an embodiment Power awareapps may use the QOS API to specify their QOS requirements that PAECmechanism (e.g., items 120 or 312) uses, e.g., as a vector, to determinethe priority of the apps. Based on the policy settings, PAEC determinesthe threshold priorities which allow wake events and builds a list ofapps that are to be frozen after system platform resume at 410. Thethreshold priority may also determine how long PAEC may defer eventsbefore it wakes up the CPU in an embodiment.

At 412, when the platform is about to enter a (e.g., S0ix) platform lowpower state, all applications are frozen and the process executionhalted (e.g., by PAEC mechanism 120 or 312), e.g., based on somepriority scheme and policy settings. “S0ix” generally refers to improvedidle power state(s) achieved by platform-level power management that isevent driven (e.g., based on OS or software application input) insteadof traditional idle power state that is periodic or based on a polledactivity. In some embodiments, at least some of the power consumptionstates discussed herein may be in accordance with those defined underAdvanced Configuration and Power Interface (ACPI) specification,Revision 4.0a, Apr. 5, 2010, including for example, C0 which mayindicate the processor is operating, C1 which may indicate the processoris not executing instructions but may return to an executing statealmost instantaneously, C2 which may indicate the processor is tomaintain all software-visible information but may take longer to returnto full executing state, C3 which may indicate the processor is sleepand does not need to keep its cache coherent, etc.

In one embodiment, PAEC mechanism (e.g., items 120 or 312) freezesapplication(s) based on the information obtained during applicationregistration or invocation. In some embodiments, at 412, for exceptionalapps that PAEC should not freeze, PAEC may be configured to assign thehighest/lowest priority available to those applications to allow fortheir wake events to land in the CPU accordingly. PAEC may send anotification about these apps to user (if configured), for example, viathe PAEC UI 314, or log information about these apps. This allows theuser to override the default settings in the future.

At 414, based on the configuration settings, PAEC mechanism (e.g., items120 or 312) may allow or restrict selective apps to wake thesystem/processor or be run post resume (from a low power consumptionstate such as S0ix) to keep the corresponding sub-system in a low-powerstate and increase the CPU residency in the low power state. Also, PAECmechanism (e.g., items 120 or 312) may keep track of the wake eventsduring platform (e.g., S0ix) low power consumption state(s) to providefeedback on the policy settings to the policy manager for fine tuning ofthe parameters. This allows PAEC to be adaptive, e.g., by keeping trackof the wake events during runtime.

In various embodiments, PAEC is establishes a relationship betweenapplications and sub-system power states to provide greater flexibilityto OS/applications/Power Manager logic to reduce power in a verygranular fashion. Also, PAEC may be adaptive and may not impact the QOSor user experience in the platform. In some embodiments, PAEC isconfigurable and may be integrated with other components such as malwareprogram, parental control, etc. to restrict specific apps. PAEC mayreduce wakes and keep a CPU in longer idle states. App developers mayleverage the QOS API to improve user experience with enhanced powersavings. In some embodiments, PAEC associates applications with platformsub-system operational modes and provides options to wake/run selectiveapplications after resuming from low power states (such as wakes fromS0ix states).

In an embodiment, PAEC is capable of masking wake events from selectivesub-systems/apps based on policy settings. Further, PAEC may coalesceand deliver low priority wakes at a later time frame. And, PAEC mayfreeze applications based on their priority settings and/or theirassociated sub-system status, e.g., to avoid sub-systems to be turned onduring low power (e.g., S0ix) states, without compromising userexperience or QOS. There may also be more user control of theconfiguration “knobs” per-application-basis (for security optimization,etc.). And, PAEC may provide the ability to securely store the policysettings on the secure storage.

In some embodiments, PAEC may provide several advantages including oneor more of the following: (1) An ability to assign priorities to theapplications in the platform and associate the applications with thesub-system operating modes. Priorities may be assigned by appsprovider/system administrator/service provider or based on userconfigurable policy settings as well. Moreover, an embodiment allowsapps to be categorized based on their priority, for example, to provideeasier app management. (2) PAEC may be configured to halt/freeze appsthat are masked out in a overlay region to avoid their events. (3) PAECprovides mechanism to wake up selective applications and theirassociated sub-system based on configuration settings. PAEC providesfine granular control from OS/app perspective. (4) PAEC may beadaptive—e.g., track the wakes during suspended state and providesfeedback to fine tune the parameters. (5) Increases the residency of theCPU and other sub-systems in deepest low power state. (6) Store userconfiguration policy in a tamper-proof, secure storage.

FIG. 5 illustrates a block diagram of a computing system 500 inaccordance with an embodiment of the invention. The computing system 500may include one or more central processing unit(s) (CPUs) 502 orprocessors that communicate via an interconnection network (or bus) 504.The processors 502 may include a general purpose processor, a networkprocessor (that processes data communicated over a computer network503), or other types of a processor (including a reduced instruction setcomputer (RISC) processor or a complex instruction set computer (CISC)).Moreover, the processors 502 may have a single or multiple core design.The processors 502 with a multiple core design may integrate differenttypes of processor cores on the same integrated circuit (IC) die. Also,the processors 502 with a multiple core design may be implemented assymmetrical or asymmetrical multiprocessors. In an embodiment, one ormore of the processors 502 may be the same or similar to the processors102 of FIG. 1. For example, one or more of the processors 502 mayinclude the PAEC logic 120 discussed with reference to FIGS. 1-4. Also,the operations discussed with reference to FIGS. 1-4 may be performed byone or more components of the system 500.

A chipset 506 may also communicate with the interconnection network 504.The chipset 506 may include a memory control hub (MCH) 508. The MCH 508may include a memory controller 510 that communicates with a memory 512(which may be the same or similar to the memory 114 of FIG. 1). Thememory 512 may store data, including sequences of instructions, that maybe executed by the CPU 502, or any other device included in thecomputing system 500. For example, the memory 512 may store the PAEC312, OS 313, and/or PAEC UI 314 discussed with reference to FIGS. 3-4.In one embodiment of the invention, the memory 512 may include one ormore volatile storage (or memory) devices such as random access memory(RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM),or other types of storage devices. Nonvolatile memory may also beutilized such as a hard disk. Additional devices may communicate via theinterconnection network 504, such as multiple CPUs and/or multiplesystem memories.

The MCH 508 may also include a graphics interface 514 that communicateswith a display device 516. In one embodiment of the invention, thegraphics interface 514 may communicate with the display device 516 viaan accelerated graphics port (AGP). In an embodiment of the invention,the display 516 (such as a flat panel display) may communicate with thegraphics interface 514 through, for example, a signal converter thattranslates a digital representation of an image stored in a storagedevice such as video memory or system memory into display signals thatare interpreted and displayed by the display 516. The display signalsproduced by the display device may pass through various control devicesbefore being interpreted by and subsequently displayed on the display516.

A hub interface 518 may allow the MCH 508 and an input/output controlhub (ICH) 520 to communicate. The ICH 520 may provide an interface to110 device(s) that communicate with the computing system 500. The ICH520 may communicate with a bus 522 through a peripheral bridge (orcontroller) 524, such as a peripheral component interconnect (PCI)bridge, a universal serial bus (USB) controller, or other types ofperipheral bridges or controllers. The bridge 524 may provide a datapath between the CPU 502 and peripheral devices. Other types oftopologies may be utilized. Also, multiple buses may communicate withthe ICH 520, e.g., through multiple bridges or controllers. Moreover,other peripherals in communication with the ICH 520 may include, invarious embodiments of the invention, integrated drive electronics (IDE)or small computer system interface (SCSI) hard drive(s), USB port(s), akeyboard, a mouse, touch screen, camera, parallel port(s), serialport(s), floppy disk drive(s) digital output support (e.g., digitalvideo interface (DVI)), or other devices.

The bus 522 may communicate with an audio device 526, one or more diskdrive(s) 528, and a network interface device 530 (which is incommunication with the computer network 503). Other devices maycommunicate via the bus 522. Also, various components (such as thenetwork interface device 530) may communicate with the MCH 508 in someembodiments of the invention. In addition, the processor 502 and the MCH508 may be combined to form a single chip. Furthermore, the graphicsaccelerator 516 may be included within the MCH 508 in other embodimentsof the invention.

Furthermore, the computing system 500 may include volatile and/ornonvolatile memory (or storage). For example, nonvolatile memory mayinclude one or more of the following: read-only memory (ROM),programmable ROM (PROM), erasable PROM (EPROM), electrically EPROM(EEPROM), a disk drive (e.g., 528), a floppy disk, a compact disk ROM(CD-ROM), a digital versatile disk (DVD), flash memory, amagneto-optical disk, or other types of nonvolatile machine-readablemedia that are capable of storing electronic data (e.g., includinginstructions).

FIG. 6 illustrates a computing system 600 that is arranged in apoint-to-point (PtP) configuration, according to an embodiment of theinvention. In particular, FIG. 6 shows a system where processors,memory, and input/output devices are interconnected by a number ofpoint-to-point interfaces. The operations discussed with reference toFIGS. 1-5 may be performed by one or more components of the system 600.

As illustrated in FIG. 6, the system 600 may include several processors,of which only two, processors 602 and 604 are shown for clarity. Theprocessors 602 and 604 may each include a local memory controller hub(MCH) 606 and 608 to enable communication with memories 610 and 612. Thememories 610 and/or 612 may store various data such as those discussedwith reference to the memory 512 of FIG. 5.

In an embodiment, the processors 602 and 604 may be one of theprocessors 502 discussed with reference to FIG. 5. The processors 602and 604 may exchange data via a point-to-point (PtP) interface 614 usingPtP interface circuits 616 and 618, respectively. Also, the processors602 and 604 may each exchange data with a chipset 620 via individual PIPinterfaces 622 and 624 using point-to-point interface circuits 626, 628,630, and 632. The chipset 620 may further exchange data with a graphicscircuit 634 via a graphics interface 636, e.g., using a PtP interfacecircuit 637.

At least one embodiment of the invention may be provided within theprocessors 602 and 604. For example, the PAEC logic 120 of FIGS. 1-4 maybe located within the processors 602 and 604. Other embodiments of theinvention, however, may exist in other circuits, logic units, or deviceswithin the system 600 of FIG. 6. Furthermore, other embodiments of theinvention may be distributed throughout several circuits, logic units,or devices illustrated in FIG. 6.

The chipset 620 may communicate with a bus 640 using a PtP interfacecircuit 641. The bus 640 may communicate with one or more devices, suchas a bus bridge 642 and I/O devices 643. Via a bus 644, the bus bridge642 may communicate with other devices such as akeyboard/mouse/touchscreen/camera 645, communication devices 646 (suchas modems, network interface devices, or other communication devicesthat may communicate with the computer network 503), audio I/O device647, and/or a data storage device 648. The data storage device 648 maystore code 649 that may be executed by the processors 602 and/or 604.

In various embodiments of the invention, the operations discussedherein, e.g., with reference to FIGS. 1-6, may be implemented ashardware (e.g., logic circuitry), software, firmware, or combinationsthereof, which may be provided as a computer program product, e.g.,including (e.g., a non-transitory) machine-readable or computer-readablemedium having stored thereon instructions (or software procedures) usedto program a computer to perform a process discussed herein. Themachine-readable medium may include a storage device such as thosediscussed with respect to FIGS. 1-6.

Additionally, such computer-readable media may be downloaded as acomputer program product, wherein the program may be transferred from aremote computer (e.g., a server) to a requesting computer (e.g., aclient) by way of data signals embodied in a carrier wave or otherpropagation medium via a communication link (e.g., a bus, a modem, or anetwork connection).

Reference in the specification to “one embodiment,” “an embodiment,” or“some embodiments” means that a particular feature, structure, orcharacteristic described in connection with the embodiment(s) may beincluded in at least an implementation. The appearances of the phrase“in one embodiment” in various places in the specification may or maynot be all referring to the same embodiment.

Also, in the description and claims, the terms “coupled” and“connected,” along with their derivatives, may be used. In someembodiments of the invention, “connected” may be used to indicate thattwo or more elements are in direct physical or electrical contact witheach other. “Coupled” may mean that two or more elements are in directphysical or electrical contact. However, “coupled” may also mean thattwo or more elements may not be in direct contact with each other, butmay still cooperate or interact with each other.

Thus, although embodiments of the invention have been described inlanguage specific to structural features and/or methodological acts, itis to be understood that claimed subject matter may not be limited tothe specific features or acts described. Rather, the specific featuresand acts are disclosed as sample forms of implementing the claimedsubject matter.

The invention claimed is:
 1. An apparatus comprising: a processor; andlogic to allow one or more of a plurality of applications to be executedbased on policy information, corresponding to the plurality ofapplications, and after the processor is to exit a low power consumptionstate, wherein the policy information is to indicate which one of theplurality of applications is to be awakened after the processor exitsthe low power consumption state, wherein the logic is to prioritizewhich of the one or more of the plurality of applications are to beallowed to wake the processor from the low power consumption state. 2.The apparatus of claim 1, wherein the logic is to allow one or moresub-systems, corresponding to the one or more of the plurality ofapplications, to be powered on based on the policy information and afterthe processor is to exit the low power consumption state.
 3. Theapparatus of claim 2, wherein the policy information is to indicatewhich of the one or more sub-systems corresponds to which of the one ormore of the plurality of applications.
 4. The apparatus of claim 2,wherein the policy information is to indicate which power state of theone or more sub-systems corresponds to which of the one or more of theplurality of applications.
 5. The apparatus of claim 1, wherein theplurality of applications comprise one or more platform-power-aware orone or more platform-power-unaware applications.
 6. The apparatus ofclaim 1, wherein the processor comprises a plurality of processor cores.7. The apparatus of claim 1, wherein two or more of a memory, theprocessor, and the logic are on a same integrated circuit device.
 8. Acomputer-readable medium to store instructions that when executed by aprocessor cause the processor to: allow one or more of a plurality ofapplications to be executed based on policy information corresponding tothe plurality of applications, and after the processor exits a low powerconsumption state, wherein the policy information indicates which one ofthe plurality of applications is to be awakened after the processorexits the low power consumption state, wherein the instructions causethe processor to prioritize which of the one or more of the plurality ofapplications are allowed to wake the processor from the low powerconsumption state.
 9. The computer-readable medium of claim 8, whereinthe instructions cause the processor to allow one or more sub-systems,corresponding to the one or more of the plurality of applications, to bepowered on based on the policy information and after the processor exitsthe low power consumption state.
 10. The computer-readable medium ofclaim 9, wherein the policy information indicates which of the one ormore sub-systems corresponds to which of the one or more of theplurality of applications.
 11. The computer-readable medium of claim 9,wherein the policy information indicates which power state of the one ormore sub-systems corresponds to which of the one or more of theplurality of applications.
 12. The computer-readable medium of claim 8,wherein the plurality of applications comprises one or moreplatform-power-aware or one or more platform-power-unaware applications.13. The computer-readable medium of claim 8, wherein a memory, coupledto the processor, is to store an operating system software.